feat(plugin): adopt Agent Plugins 1.0 and cover every coding agent - #13
Merged
Conversation
The plugin advertised `api.agentdrive.run/mcp`, a host that no longer resolves, so every install path in this repo wired agents to a dead endpoint. Repoint all of them at the live transport, `https://drive.mcp.tokencanopy.com/mcp` (ADR-0002). Adopt Agent Plugins 1.0 (agent-plugins.org), the vendor-neutral packaging standard published 2026-08-06 and supported by ChatGPT, Codex, Cursor, Copilot, Kiro and VS Code. The repo already carried `.agents/plugins/marketplace.json` but neither file the standard actually requires, so no conformant client could load it: plugin/plugin.json manifest, only the ten permitted top-level fields plugin/mcp.json streamable-http server, no auth keys — the standard leaves authorization client-managed, deliberately Add `plugin/.codex-plugin/plugin.json`, which was missing entirely; Codex reads its manifest from that path and found nothing. Anthropic is not among the standard's launch adopters, so Claude Code keeps its own `.claude-plugin/` manifest and `plugin/.mcp.json`. That is now the only per-vendor manifest carrying weight. `docs/add-to-your-agent.md` covers nine clients. Each spells the same URL differently — `url`, `serverUrl`, `httpUrl`, and `servers` vs `mcpServers` — so the per-client instructions cannot be collapsed. Zed gets the `mcp-remote` bridge because its native remote-HTTP support is inconsistent across releases. `connector/server.json` gets the live endpoint. Its `run.agentdrive/agentdrive` namespace is left alone on purpose: renaming it is a registry republish against a retired domain, which is a human decision. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01W1nxC2LaqTPrix7CL4Ehuv
jiashuoz
added a commit
that referenced
this pull request
Sep 4, 2026
The MCP Registry entry was corrected on 2026-09-04. `run.agentdrive/agentdrive` 0.1.0 is now live and serves the canonical transport: https://drive.mcp.tokencanopy.com/mcp PR #13 fixed the URL in this file but left `version` at 0.0.1, which the registry will not accept as an update — a republish needs a new version. The publish therefore went out as 0.1.0 and this file was left behind it. Bring them back into agreement. The previous 0.0.1 entry, which pointed at the retired `api.agentdrive.run/mcp` (NXDOMAIN), is now marked `deprecated` in the registry rather than deleted: it is a real historical version, and deprecating it keeps a version-pinned client from resolving a dead host. A default `version=latest` lookup returns only 0.1.0. Note that editing this file does not itself publish anything. The live listing is updated by `mcp-publisher`, authenticated by a DNS-verified key on the namespace's domain. Claude-Session: https://claude.ai/code/session_01W1nxC2LaqTPrix7CL4Ehuv Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Every install path in this repo wired agents to
api.agentdrive.run/mcp— a host that no longer resolves. Repoint them all at the live transport,https://drive.mcp.tokencanopy.com/mcp(ADR-0002).Then adopt Agent Plugins 1.0, the vendor-neutral packaging standard published 2026-08-06 (Amazon, Cursor, Microsoft, OpenAI, Vercel; ChatGPT, Codex, Cursor, Copilot, Kiro and VS Code supporting at launch). The repo already carried
.agents/plugins/marketplace.jsonbut neither file the standard actually requires, so no conformant client could load it.Changes
New — the standard:
plugin/plugin.json— manifest, restricted to the ten permitted top-level fieldsplugin/mcp.json—type: "streamable-http", no auth keys (the standard leaves authorization client-managed, deliberately)New — Codex:
plugin/.codex-plugin/plugin.jsonwas missing entirely. Codex reads its manifest from that path and found nothing.Claude Code keeps its own
.claude-plugin/manifest andplugin/.mcp.json— Anthropic is not among the standard's launch adopters, so this is now the only per-vendor manifest carrying weight.docs/add-to-your-agent.mdcovers nine clients: Claude Code, Claude Desktop/web, Codex, Cursor, VS Code/Copilot, Windsurf, Gemini CLI, Zed, and any Agent Plugins 1.0 client.These instructions can't be collapsed into one block, because every client spells the same URL differently:
plugin/mcp.jsontype: "streamable-http"+url.mcp.jsontype: "http"+url~/.codex/config.tomlurl+auth = "oauth".cursor/mcp.jsontype: "streamable-http"+url.vscode/mcp.jsonservers(notmcpServers) +urlmcp_config.jsonserverUrl~/.gemini/settings.jsonhttpUrlcontext_serversmcp-remotebridgeZed gets the bridge rather than a direct URL because its native remote-HTTP support is inconsistent across releases.
Deliberately not changed
connector/server.jsongets the live endpoint but keeps itsrun.agentdrive/agentdrivename. Renaming it means a registry republish DNS-verified against a domain that has been retired — a human decision, not a mechanical one. Until that happens, this file rather than the live registry listing is the source of truth for the endpoint.Verification
plugin/plugin.jsoncarries only the spec's permitted top-level fields.name,description) intact.plugin/commands/*.mdcontain no URLs.Notes
License corrected to
MITacross all four manifests to matchLICENSE; two of them previously disagreed.🤖 Generated with Claude Code
https://claude.ai/code/session_01W1nxC2LaqTPrix7CL4Ehuv